Customizable Gestures For Mobile Devices

ABSTRACT

Users are enabled to define and modify mappings between (1) gestures and (2) actions performed by one or more computing devices in response to a device detecting performance of a gesture. A generalized gesture-to-action mapping framework allows users to intuitively define and modify such mappings. In response to a device detecting the performance of a particular gesture, one or more devices may cause the execution of one or more device actions based on a set of user-defined gesture-to-action mappings.

RELATED APPLICATION DATA AND CLAIM OF PRIORITY

This application is a Continuation of prior U.S. patent application Ser.No. 13/405,708 (Attorney Docket No. 50269-1439) entitled “CustomizableGestures For Mobile Devices”, filed Feb. 27, 2012, the contents of whichare incorporated herein by reference for all purposes.

FIELD OF THE INVENTION

The present invention generally relates to using gestures as input tocomputing devices, and, more specifically, to a system for allowing auser to customize mappings between gestures and actions performed inresponse to gesture detection.

BACKGROUND

The way in which users interact with modern computing devices such aspersonal computers, smart phones, and tablet computers is becomingincreasingly sophisticated. For example, traditional client device inputmechanisms such as keyboards, computer mice, and numeric keypads are nowfrequently being supplemented and sometimes replaced entirely by userinterfaces that detect gestures as input. Common gesture-based inputsinclude, for example, the motion of a user's finger on a touch-enabledinterface, the detected physical movement of a device by a user, and auser performing bodily motions that are visually detected by a cameraconnected to a device. Furthermore, the increasing variety andcapabilities of input sensors available on client devices is leading toa nearly limitless range of such gesture-based input methods.

However, despite the advances in the user interface experience enabledby gesture-based input mechanisms, existing gesture-based input systemson client devices are generally restrictive in their implementation.Users of such gesture-based input systems generally lack the ability tointuitively control the association between gestures and the actionsperformed in response to a client device detecting the performance of aparticular gesture. Typically, gesture-to-action associations areprogrammed by application developers into the system and applicationsrunning on a client device and the only gesture-to-action mappingsavailable to users are those provided by the application developers.Furthermore, the device on which the actions are performed in responseto a particular gesture is generally confined to the device detectingperformance of the gesture. These restrictions fail to recognize thatusers typically interact on a daily basis with a number of separatedevices in many different settings and would benefit from customizablegesture-based interactions on and between those devices.

Furthermore, existing gesture-based input systems generally fail to takeadvantage of information related to the operating context of clientdevices in order to better customize gesture-to-action mappings. Thesensors available on modern client devices make available a wealth ofinformation related to the environment in which the device is currentlybeing used. However, existing gesture-based input systems typicallyemploy the same gesture-to-action mappings irrespective of changes inthe operating environment context of a device and without taking intoconsideration user preferences related to those contexts.

The approaches described in this section are approaches that could bepursued, but not necessarily approaches that have been previouslyconceived or pursued. Therefore, unless otherwise indicated, it shouldnot be assumed that any of the approaches described in this sectionqualify as prior art merely by virtue of their inclusion in thissection.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings:

FIG. 1 illustrates a user interface for selecting one or more gesturesfor the definition of a gesture-to-action mapping according to anembodiment;

FIG. 2 illustrates a user interface for selecting one or more actionsfor the definition of a gesture-to-action mapping according to anembodiment;

FIG. 3 is a flowchart illustrating an example process for usinggesture-to-action mappings according to an embodiment;

FIG. 4. is a block diagram that illustrates a client device upon whichan embodiment described herein may be implemented.

FIG. 5 is a block diagram that illustrates a computer system upon whichan embodiment described herein may be implemented.

DETAILED DESCRIPTION

In the following description, for the purposes of explanation, numerousspecific details are set forth in order to provide a thoroughunderstanding of the present invention. It will be apparent, however,that the present invention may be practiced without these specificdetails. In other instances, well-known structures and devices are shownin block diagram form in order to avoid unnecessarily obscuring thepresent invention.

Subject matter will now be described more fully hereinafter withreference to the accompanying drawings, which form a part hereof, andwhich show, by way of illustration, specific example embodiments.Subject matter may, however, be embodied in a variety of different formsand, therefore, covered or claimed subject matter is intended to beconstrued as not being limited to any example embodiments set forthherein; example embodiments are provided merely to be illustrative.Likewise, a reasonably broad scope for claimed or covered subject matteris intended. Among other things, for example, subject matter may beembodied as methods, devices, components, or systems. Accordingly,embodiments may, for example, take the form of hardware, software,firmware or any combination thereof (other than software per se). Thefollowing detailed description is, therefore, not intended to be takenin a limiting sense.

Throughout the specification and claims, terms may have nuanced meaningssuggested or implied in context beyond an explicitly stated meaning.Likewise, the phrase “in one embodiment” as used herein does notnecessarily refer to the same embodiment and the phrase “in anotherembodiment” as used herein does not necessarily refer to a differentembodiment. It is intended, for example, that claimed subject matterinclude combinations of example embodiments in whole or in part.

Overview

Techniques are described herein that provide the ability to define andmodify mappings between (1) gestures and (2) actions performed by one ormore computing devices in response to a client device detectingperformance of a gesture. A generalized gesture-to-action mappingframework allowing users to intuitively define and modify such mappingsis disclosed. In response to a client device detecting the performanceof a particular gesture, one or more devices may cause the execution ofone or more device actions based on a set of user-definedgesture-to-action mappings.

In one embodiment, user-defined gesture-to-action mappings are furtherassociated with one or more defined device contexts. The device contextsmay include one or more variables associated with the operatingenvironment of a device. For example, any combination of a particulargeographical location, time of day, particular user accounts, and otherdetectable devices in the range of a device may serve as device contextvariables. A particular gesture-to-action mapping associated with one ormore contexts may be applicable only when a gesture is detected in oneof the associated contexts.

In one embodiment, user-defined gesture-to-action mappings areassociated with a device hierarchy. A device hierarchy may define asystem of precedence between multiple devices detecting a gesture in acontext including other devices. In other words, a particulargesture-to-action mapping may depend on the context of other devicespresent when the gesture is detected. For example, if a first devicedetects the performance of a particular gesture in the presence ofsecond device that takes precedence over the first device in anassociated device hierarchy, the actions associated with thegesture-to-action mappings may not be performed. However, if the firstdevice detects the same gesture in the absence of the dominating seconddevice, the associated actions are performed.

Gestures

Gestures, as described herein, include a variety of input eventsdetectable by client devices. Similar to the manner in which a key presson a keyboard or a button click on a computer mouse signals to anassociated computing device a particular input, performance of a gesturemay signal a particular input to a client device recognizing the gestureperformance. In an embodiment, the implementation of gesture-basedinputs on a client device may be facilitated by one or more gesturetraining and recognition algorithms.

Gestures include and are generally associated with human bodilymovement, but are not limited to bodily movement and include a varietyof events detectable by a computing device as further described herein.A client device may be enabled to recognize the performance of a gestureusing a variety of input devices and sensors including, for example,touch-enabled interfaces, cameras, microphones, controller devices, andother similar devices and sensors. Furthermore, the definition of aparticular gesture in a gesture recognition system is not limited to asingle form or instance of gesturing, and may include any combinationand/or repetition of gesturing events.

Gestures may be based on one or more types of motion. For example, agesture may include motion performed by a user that is detected by aclient device. Motion-based gestures include gestures based on touch,such as, for example, a user making particular motions in contact with atouch-enabled interface. A user may signal the performance of a gestureusing a touch-enabled input device by, for example, making a swiping,pinching, or tapping motion in contact with a touch-enabled inputdevice. For example, the surface of a touch-enabled interface mayrepresent a two-dimensional plane upon which a user may make particularmotions in contact with the interface. As another example, theapplication of varying levels of force to a touch-enabled interface maysignal the performance of a particular gesture.

The detected motion of the device itself may also signal the performanceof a particular gesture. For example, a computing device may includegyroscopic or other similar sensors capable of detecting and measuringthe relative spatial orientation of the device. A device including asensor capable of determining the device's spatial orientation may beenabled to detected gestures involving motion of the device such as, forexample, a user shaking the device or causing other detectable patternsof device motion.

Motion that is not made in direct contact with a device may also bedetected and signal the performance of a gesture. For example, a cameraor other sensor capable of detecting motion external to a device may beenabled to detect particular motions made by a user or other object asgestures. For example, the movement of a user's hands or other parts ofthe body in a particular pattern may be visually detected as a gestureby an attached camera or other similar sensor. A device's visualdetection of gestures may be relative to motion in a particulardimensioned space such as, for example, a two-dimensional plane or athree-dimensional space.

Gestures may also include sounds or other non-tangible and non-visualinputs. For example, a client device may detect a particular pattern ofspeech or other detectable noise as a gesture. Gestures based on soundmay originate from either human or non-human sources, such as, forexample, an alarm sounding or a dog barking.

Device Actions

Device actions, as described herein, comprise one or more steps that maybe performed programmatically or otherwise by a computing device. Forexample, an action performed by a smart phone may result in sending aShort Message Service (SMS) message, an action performed by a televisionmay result in increasing the volume of the television one unit, and anaction performed by a desktop computer may result in the execution of aparticular installed application. The steps corresponding to aparticular action may be performed entirely on a single device, or mayinvolve interaction between multiple devices, which may include devicesother than a device detecting performance of a gesture associated withthe action.

Device actions may cause a single computational step, or any combinationof multiple steps. For example, an action may correspond to the singlestep of sending an SMS message to a particular user, or an action mayinclude multiple steps such as an action comprising the steps of turningon a television and changing the channel to a particular channel.

Device Contexts

The context of a client device, as described herein, may be defined byany number of variables detectable by a client device and relating tothe operating environment of the device. In one embodiment, devicecontexts may be used to refine gesture-to-action mappings by associatingthe applicability of particular gesture-to-action mappings relative toone or more defined contexts. For example, a device associated with aparticular gesture-to-action mapping X that has been associated with aparticular context Y may be enabled to apply gesture-to-action mapping Xonly if the device detects the gesture performance and also detects thepresence of context Y.

A device context may be associated with a detected geographical locationof the device. Client devices are often enabled to detect the device'sgeographical location based on, for example, Global Positioning Systems(GPS) or other information associated with wired or wireless networksdetectable by the device. Other examples of environmental variables uponwhich a context may be based include a time of day, day of the week,temperature, ambient light, or any other similar information associatedwith the device's operating environment.

A device context may also be based on the presence of other devices orentities in the proximity of the device. For example, a device may beenabled to detect other devices connected to a Local Area Network (LAN)or Personal Area Network (PAN) accessible to the device. As anotherexample, a device may be enabled with wireless technologies such as, forexample, Bluetooth®, Wi-Fi™, or other wireless technologies capable ofdetecting other devices in proximity of the device. Informationassociated with detectable devices in the proximity of a device mayinclude, for example, the number of devices in a certain range, orparticular device identification information including the type ofdevice, capabilities, ownership information, or any other informationidentifying characteristics of the device.

Device contexts may be based on particular applications executing orpresent on a device. For example, a first context may be associated witha device when a particular chat application is being executed on thedevice, and a second context may be associated with the device when aweb browser application is executing. The definition of contexts basedon particular applications allows users to establish gestures to actionmappings that are specific to the characteristics of the application.For example, it may make intuitive sense for a user to define agesture-to-action mapping for the context of a web browser such thatwhen a particular swiping motion is detected, the web browser displaysthe previous web page in the browser's history. The user may define agesture-to-action mapping based on the same swiping motion gesture tocause a different action in the context of a chat application, forexample, causing the chat application to send a particular message.

In one embodiment, device contexts may be relative to individual usersbased on user accounts. A client device may support user accounts thatauthenticate individual users with the client device, and a context maytake into account the particular user that is currently logged on to theclient device. For example, a particular device detecting a number ofdevices in the proximity of the device may detect one of severalcontexts depending on the particular user accounts that are currentlyassociated with each of the detected devices.

Device Hierarchies

In one embodiment, a hierarchy of devices is defined in order to furtherrefine the application of gesture-to-action mappings. A device hierarchymay define an ordered relationship between two or more devices for thepurpose of establishing precedence between the devices. The relativeprecedence between two or more devices may be used, for example, in acase where a device detects a particular gesture event in a contextincluding one or more other devices. For example, a device hierarchy maybe defined that establishes that device X has precedence over device Yrelative to gesture-to-action mapping Z. According to the example devicehierarchy, if device Y detects the performance of a gesture defined inmapping Z in a context that includes device X, the actions associatedwith mapping Z may be prohibited from occurring based on the dominanceof device X. However, if device Y later detects the performance of agesture defined in mapping Z in a context that does not include deviceX, the actions may be performed.

In another embodiment, the relative precedence between two or moredevices may be used, for example, in a case where two or more devicessimultaneously detect the performance of the gesture and a user woulddesire that only one of the device's gesture-to-action mappings beevaluated based on the detected gesture. For example, if both device Xand device Y detect the occurrence of a particular gesture, and a devicehierarchy is defined indicating that device X takes precedence in thehierarchy over device Y, then only the gesture-to-action mappingsassociated with device X would be consulted.

In another embodiment, device hierarchies are relative to particularcontexts. For example, a first device hierarchy may be defined for a setof devices relative to a first device context such as, for example, acontext defined by a geographical area corresponding to a user's home. Asecond device hierarchy may be defined relative to a second devicecontext such as, for example, a device context defined by a geographicalarea corresponding to the location where the user works. If devices X orY then detect the performance of a particular gesture, a differentdevice hierarchy may be applied based on the particular context (i.e.,in the context of the user's home or the user's work).

Gesture-to-Action Mapping System Overview

In one embodiment, a gesture-to-action mapping system enables users tocreate, modify, and delete user-defined gesture-to-action mappings. Inan embodiment, a user may create, modify, and delete user-definedmappings with the use of a graphical interface. FIG. 1 illustrates anexample graphical user interface 100 as part of an example systemallowing users to define custom gesture-to-action mappings. Inparticular, graphical user interface 100 illustrates multiple interfacecomponents designed to assist the process of selecting a gesture for thecreation of a new gesture-to-action mapping or to modify an existingmapping. Graphical user interface 100 is not a development environmentfor the development of software, but rather, in an embodiment, graphicaluser interface 100 is an interface for the definition ofgesture-to-action mappings without the need for a user to compile sourcecode.

Interface component 102 illustrates an example drop-down menu componentallowing for the selection of a particular gesture category that hasassociated with it one or more related gestures. In an embodiment, theselection of a particular gesture category using interface component 102causes the display of a selectable list of gestures associated with theselected gesture category. For example, gestures may be categorizedaccording to the number of spatial dimensions required for theperformance of the gesture (e.g., two-dimensional gestures performed ona two-dimensional touch interface or three-dimensional gesturesperformed and detected by a camera device). The grouping of gestures mayassist locating a particular gesture or gesture type and may also helpconserve the amount of screen space required to display gesturesavailable for mapping.

Interface component 104 illustrates an example selectable list itemrepresenting an available gesture for use in the definition of agesture-to-action mapping. In an embodiment, gestures may be associatedwith one or more labels used for display in a graphical interface suchas, for example, a customizable text description and a graphicaldepiction of a pattern associated with the gesture. For example, thezigzag arrow pattern illustrated on interface component 104 may bedisplayed to indicate that performance of the gesture corresponding tothe particular list item involves a patterned motion similar to that ofthe pattern graphically depicted.

In another embodiment, one or more gestures not previously defined inthe gesture-to-action mapping system may be created for use in agesture-to-action mapping. Interface component 106 illustrates anexample button that may be selected in order initiate a process fordefining a new gesture. Example embodiments may employ a gesturerecognition engine in order to assist a user in defining a new gesture.In an embodiment, after a new gesture has been defined by a user, thegesture may then be stored in the gesture-to-action mapping system anddisplayed in the list of selectable gestures or automatically selectedfor processing in the subsequent mapping steps. In another embodiment,the process of defining or modifying a gesture may be independent of thegesture-to-action mapping process, and may be enabled to allow users tocreate or modify gestures for later use in mappings.

In an embodiment, graphical user interface 100 includes additionalbuttons to assist the process of defining new gesture-to-actionmappings. For example, help button 110 may be included in order toprovide documentation relevant to the gesture-to-action mapping processin response to a user selecting the button. After the selection of oneor more gestures, next button 118 may be selected in order to advancethe system to a subsequent processing step.

FIG. 2 illustrates an example graphical user interface 200 assisting inthe selection of one or more actions for the definition of a particulargesture-to-action mapping. Similar to graphical user interface 100,graphical user interface 200 includes multiple interface components toassist the selection of the one or more actions. Interface component 202illustrates an example of a drop-down menu component allowing for theselection of a particular category of actions. The options in thedrop-down menu of interface component 202 may represent variouscategories of actions including, for example, categorizations based onthe type of action, the device performing the action, or otheruser-defined categories of actions.

In an embodiment, the selection of a particular action category frominterface component 202 causes a corresponding selectable list of deviceactions to be displayed on graphical user interface 200. Interfacecomponent 204 illustrates an example selectable list item representing aparticular action a user may select as part of a gesture-to-actionmapping definition. Similar to the display of selectable gestures, in anembodiment, each action may be represented in a selectable list by anycombination of word labels or graphical depictions representing thecorresponding action.

In an embodiment, the actions displayed and available for use in amapping may include actions previously defined in the system or by auser in other gesture-to-action mappings. In another embodiment, one ormore new actions may be defined for addition to the list of availableactions. For example, an additional process may guide a user through thedefinition of a new user-defined action allowing the user to specify oneor more steps to include in the performance of the user-defined action.A new user-defined action may then be stored and selected for use in thegesture-to-action mapping under definition or in futuregesture-to-action mappings.

In one embodiment, in addition to the selection of one or more deviceactions, an additional interface may assist in the selection of one ormore device contexts to be associated with a gesture-to-action mappingunder definition. As described above, a device context represents one ormore variables associated with the operating environment of a device. Inan embodiment, device contexts available for selection may be contextspreviously defined in the system, or additional interfaces may beprovided to assist in the definition of a new device context. Forexample, an interface may assist a user in determining and specifyingvarious context variables to include in the definition of a particulardevice context.

Interface component 206 illustrates a button enabling confirmation ofone or more actions selected for use in a current gesture-to-actionmapping under creation. In an embodiment, the selection of interfacecomponent 206 may direct a user to a confirmation screen displaying thecurrently selected gestures, actions, and contexts, if applicable. Afterfurther review or modification, in an embodiment, the selected gestures,actions, and contexts may be confirmed, resulting in the storing of anew or modified gesture-to-action mapping in the gesture-to-actionmapping system.

In one embodiment, one or more additional interfaces may be provided forthe definition of a device hierarchy. In order to facilitate defining adevice hierarchy, in an embodiment, one or more devices may beregistered with a centralized device registration module. Thecentralized device registration module may store one or more identifierscorresponding to each particular device registered in the module. In anembodiment, an interface enables a user to order the registered devicesto establish a particular device hierarchy. In another embodiment, theinterface enables a user to associate a particular device hierarchy withone or more particular device contexts.

In one embodiment, a defined device hierarchy may be stored on a clientdevice. In another embodiment, a defined device hierarchy is stored on aremote server. A remote server storing a device hierarchy may include acentralized device registration module. In order to support storingdevice hierarchies for multiple users, a remote server may associatedevice hierarchies with a user account.

Defining Gesture-to-Action Mappings

FIG. 3 illustrates a flow diagram with steps corresponding to use of agesture-to-action mapping system similar to the system described herein.In block 302, a user interface is presented that includes interfacecomponents associated with defining a mapping between a gesture and anaction. In an embodiment, a user may define one or more mappingvariables associated with a gesture-to-action mapping, as describedherein, using the user interface.

In block 304, one or more gesture-to-action mappings are stored usingone or more of the techniques described herein. In one embodiment,gesture-to-action mappings are stored and accessed directly on a clientdevice. For example, one or more gesture-to-action mappings may bestored in one or more tables on a mobile device belonging to a user. Ifa mobile device detects the performance of a gesture, the mobile devicemay consult the one or more gesture-to-action mappings stored in thetables on the client device. In another embodiment, gesture-to-actionmappings are stored on a centralized device that is accessible by one ormore client devices over a wired or wireless network. The centralizeddevice may be, for example, a particular client device on a LAN, or aremote server accessible over the Internet.

In block 306, a device storing one or more gesture-to-action mappingsreceives an indication that a particular gesture has been performed. Inan embodiment, a gesture recognition engine detects the performance of agesture and sends the indication of the gesture's performance. In oneembodiment, a gesture recognition engine sends notification to anothermodule running on the same device as the device detecting the gesture.In another embodiment, a device detecting the performance of a gesturemay send a request to a centralized device storing gesture-to-actionmappings. In one embodiment, a device detecting the performance of thegesture further determines and indicates one or more device contextvariables associated with the device.

In block 308, in response to receiving an indication that a particulargesture has been performed, a device storing one or moregesture-to-action mappings determines one or more actions associatedwith the performed gesture based on the gesture-to-action mappings. Inan embodiment, the step of determining the one or more actionsassociated with the performed gesture is further based on the one ormore device context variables determined by the device.

In block 310, the device determining the one or more actions associatedwith the performed gesture based on the gesture-to-action mappingscauses the performance of one or more actions specified in the mappings.The actions to be performed may be performed on one or more devicesincluding the device storing the mappings and other devices. In variousembodiments, the performance of actions may be caused by one or more ofthe execution of code, the sending of wired or wireless network signals,or other means of causing computational steps to be performed.

Gesture Packages

In one embodiment, a set of gesture-to-action mappings may be associatedwith a gesture package. A gesture package is a portable collection ofgesture-to-action mappings that may, for example, be suited for aparticular device or application. For example, a gesture package mayinclude multiple gesture-to-action mappings that are relevant to aparticular chat application on client devices. The gesture packageassociated with the chat application may include a mapping indicatingthat if a gesture corresponding to a user shaking a client device isdetected, the device will send the chat message “Hello!” to anotherclient device. If a user desires the availability of the samegesture-to-action mappings for the particular chat application onanother device, then rather than manually customizing the device withthe same gesture-to-action mappings one mapping at a time, the user maytransfer the chat application gesture package onto the device. A gesturepackage may be transferred onto a particular device by downloading,installing, or otherwise loading the gesture package on the devicedirectly from another client device, a download server, or any otherform of data storage.

In another embodiment, gesture packages may be used in order totransfer, to a client device, gesture-to-action mappings that areintended to be used only for a limited period of time or withinparticular contexts. For example, a user may define a gesture packagethat includes gesture-to-action mappings that include actions relevantto devices located within the user's home. The user may further desirethat the gesture-to-action mappings be available only for a 24-hourperiod. In such case, a user may associate one or more gesture-to-actionmappings with a gesture package associated with the desired criteria(i.e., limited to the context of the user's home and for a 24-hourperiod) and transfer the gesture package to other client devices.

Gesture Disambiguation Using Contexts

In another embodiment, defined gesture contexts may be used to assist adevice detecting a candidate gesture event in disambiguating thecandidate gesture event between two or more defined gestures. Due to theimprecise nature of human bodily motion and other gesture events,gesture recognition engines are tasked with interpreting detectedgesture events in order to determine a defined gesture to which thegesture event corresponds. For example, a user may perform a motion on atouch-enabled interface that is relatively similar to two separatelydefined gestures. A gesture recognition engine subsequently maydetermine which of the two gestures was intended by the user's motion.

In order to determine the defined gesture corresponding to a gestureevent, gesture recognition engines commonly employ a number ofmathematical algorithms in order to determine the most closelyassociated defined gesture. In one embodiment, defined device contextsmay be used in order to assist a gesture recognition engine indisambiguating a particular gesture event between two or more definedgestures. For example, in a particular set of gesture-to-actionmappings, a first gesture-to-action mapping may be associated with adevice context X, and a second gesture-to-action mapping may beassociated with a device context Y. A client device may detect aparticular gesture event in device context Y, but a gesture recognitionengine associated with the device might be unable to conclusivelydetermine whether the gesture event corresponds to a gesture associatedwith the first gesture-to-action mapping or second gesture-to-actionmapping. In the previous example, in an embodiment, the gesturerecognition engine may default to the second gesture-to-action mappingbased on the determination that the candidate gesture action took placein device context Y and the second gesture-to-action mapping isassociated with device context Y. A device context is thus used todisambiguate between two or more possible gestures based on the devicecontext associated with the device detecting the gesture performance.

Example Client Device

A client device may include a computing device capable of sending orreceiving signals, such as via a wired or a wireless network. A clientdevice may, for example, include a desktop computer or a portabledevice, such as a cellular telephone, a smart phone, a display pager, aradio frequency (RF) device, an infrared (IR) device, a Personal DigitalAssistant (PDA), a handheld computer, a tablet computer, a laptopcomputer, a set top box, a wearable computer, an integrated devicecombining various features, such as features of the forgoing devices, orthe like.

A client device may vary in terms of capabilities or features. Claimedsubject matter is intended to cover a wide range of potentialvariations. For example, a cell phone may include a numeric keypad or adisplay of limited functionality, such as a monochrome liquid crystaldisplay (LCD) for displaying text. In contrast, however, as anotherexample, a web-enabled client device may include one or more physical orvirtual keyboards, mass storage, one or more accelerometers, one or moregyroscopes, GPS or other location-identifying type capability, or adisplay with a high degree of functionality, such as a touch-sensitivecolor 2D or 3D display, for example.

A client device may include or may execute a variety of operatingsystems, including a personal computer operating system, such as aWindows, iOS or Linux, or a mobile operating system, such as iOS,Android, or Windows Mobile, or the like. A client device may include ormay execute a variety of possible applications, such as a clientsoftware application enabling communication with other devices, such ascommunicating one or more messages, such as via email, short messageservice (SMS), or multimedia message service (MIMS), including via anetwork, such as a social network, including, for example, Facebook,LinkedIn, Twitter, Flickr, or Google+, to provide only a few possibleexamples. A client device may also include or execute an application tocommunicate content, such as, for example, textual content, multimediacontent, or the like. A client device may also include or execute anapplication to perform a variety of possible tasks, such as browsing,searching, playing various forms of content, including locally stored orstreamed video, or games (such as fantasy sport leagues). The foregoingis provided to illustrate that claimed subject matter is intended toinclude a wide range of possible features or capabilities.

For example, FIG. 4. is a block diagram that illustrates a client device400 upon which an embodiment of the invention may be implemented. Clientdevice 400 includes a hardware processor 422 in communication with amass memory 430 and coupled with bus 424 for processing information.Hardware processor 422 may be, for example, a general purposemicroprocessor. Client device 400 also includes a power supply 426, oneor more network interfaces 450, an audio interface 452, input/outputinterface 460, a display 454, a keypad 456, an illuminator 458, aninput/output interface 460, a haptic interface 462, and a globalpositioning systems (GPS) receiver 464. Power supply 426 provides powerto client device 400. A rechargeable or non-rechargeable battery may beused to provide power. The power may also be provided by an externalpower source, such as an AC adapter or a powered docking cradle thatsupplements and/or recharges a battery.

Client device 400 may optionally communicate with a base station (notshown), or directly with another computing device. Network interface 450includes circuitry for coupling client device 400 to one or morenetworks, and is constructed for use with one or more communicationprotocols and technologies including, but not limited to, global systemfor mobile communication (GSM), code division multiple access (CDMA),time division multiple access (TDMA), user datagram protocol (UDP),transmission control protocol/Internet protocol (TCP/IP), SMS, generalpacket radio service (GPRS), WAP, ultra wide band (UWB), IEEE 802.16Worldwide Interoperability for Microwave Access (WiMax), SIP/RTP,Bluetooth™, infrared, Wi-Fi, Zigbee or any of a variety of otherwireless communication protocols. Network interface 450 is sometimesknown as a transceiver, transceiving device, or network interface card(MC).

Audio interface 452 is arranged to produce and receive audio signalssuch as the sound of a human voice. For example, audio interface 452 maybe coupled to a speaker and microphone (not shown) to enabletelecommunication with others and/or generate an audio acknowledgmentfor some action. Display 454 may be a liquid crystal display (LCD), gasplasma, light emitting diode (LED), or any other type of display usedwith a computing device. Display 454 may also include a touch sensitivescreen arranged to receive input from an object such as a stylus or adigit from a human hand.

Keypad 456 may comprise any input device arranged to receive input froma user. For example, keypad 456 may include a push button numeric dial,or a keyboard. Keypad 456 may also include command buttons that areassociated with selecting and sending images. Illuminator 458 may remainactive for specific periods of time or in response to events. Forexample, when illuminator 458 is active, it may backlight the buttons onkeypad 456 and stay on while the client device is powered. In addition,illuminator 458 may backlight these buttons in various patterns whenparticular actions are performed, such as dialing another client device.Illuminator 458 may also cause light sources positioned within atransparent or translucent case of the client device to illuminate inresponse to actions.

Client device 400 also comprises input/output interface 460 forcommunicating with external devices, such as a headset, or other inputor output devices not shown in FIG. 4. Input/output interface 460 canutilize one or more communication technologies, such as USB, infrared,Bluetooth™, or the like. Haptic interface 462 is arranged to providetactile feedback to a user of the client device. For example, the hapticinterface may be employed to vibrate client device 400 in a particularway when another user of a computing device is calling.

Optional GPS transceiver 464 can determine the physical coordinates ofclient device 400 on the surface of the Earth, which typically outputs alocation as latitude and longitude values. GPS transceiver 464 can alsoemploy other geo-positioning mechanisms, including, but not limited to,triangulation, assisted GPS (AGPS), E-OTD, CI, SM, ETA, BSS or the like,to further determine the physical location of client device 400 on thesurface of the Earth. It is understood that under different conditions,GPS transceiver 464 can determine a physical location within millimetersfor client device 400; and in other cases, the determined physicallocation may be less precise, such as within a meter or significantlygreater distances. In one embodiment, however, mobile device may,through other components, provide other information that can be employedto determine a physical location of the device, including for example, aMAC address, IP address, or the like.

Mass memory 420 includes a RAM 432, a ROM 434, and other storage means.Mass memory 430 illustrates another example of computer storage mediafor storage of information such as computer readable instructions, datastructures, program modules or other data. Mass memory 430 stores abasic input/output system (“BIOS”) 440 for controlling low-leveloperation of client device 400. The mass memory also stores an operatingsystem 441 for controlling the operation of client device 400. It willbe appreciated that this component may include a general purposeoperating system such as a version of UNIX, or LINUX™, or a specializedclient communication operating system such as Windows Mobile™, or theSymbian® operating system. The operating system may include, orinterface with a Java virtual machine module that enables control ofhardware components and/or operating system operations via Javaapplication programs.

Memory 430 further includes one or more data storage 444, which can beutilized by client device 400 to store, among other things, applications442 and/or other data. For example, data storage 444 may also beemployed to store information that describes various capabilities ofclient device 400. The information may then be provided to anotherdevice, including being sent as part of a header during a communication,sent upon request, or the like. Moreover, data storage 444 may also beemployed to store content and/or social networking information includingtext messages, address books, group member lists, or the like. Forexample, data storage 444 may include data, including cookies, and/orother client device data sent by a network device. Data storage 444 mayalso include image files, social networking data, location informationdata, or the like, for display and/or use through various applications.

Applications 442 may include computer executable instructions which,when executed by client device 400, provide such functions as calendars,contact managers, task managers, transcoders, database programs, wordprocessing programs, screen savers, security applications, spreadsheetprograms, games, search programs, and so forth.

Hardware Overview

According to one embodiment, the techniques described herein areimplemented by one or more special-purpose computing devices. Thespecial-purpose computing devices may be hard-wired to perform thetechniques, or may include digital electronic devices such as one ormore application-specific integrated circuits (ASICs) or fieldprogrammable gate arrays (FPGAs) that are persistently programmed toperform the techniques, or may include one or more general purposehardware processors programmed to perform the techniques pursuant toprogram instructions in firmware, memory, other storage, or acombination. Such special-purpose computing devices may also combinecustom hard-wired logic, ASICs, or FPGAs with custom programming toaccomplish the techniques. The special-purpose computing devices may bedesktop computer systems, portable computer systems, handheld devices,networking devices or any other device that incorporates hard-wiredand/or program logic to implement the techniques.

For example, FIG. 5 is a block diagram that illustrates a computersystem 500 upon which an embodiment of the invention may be implemented.Computer system 500 includes a bus 502 or other communication mechanismfor communicating information, and a hardware processor 504 coupled withbus 502 for processing information. Hardware processor 504 may be, forexample, a general purpose microprocessor.

Computer system 500 also includes a main memory 506, such as a randomaccess memory (RAM) or other dynamic storage device, coupled to bus 502for storing information and instructions to be executed by processor504. Main memory 506 also may be used for storing temporary variables orother intermediate information during execution of instructions to beexecuted by processor 504. Such instructions, when stored innon-transitory storage media accessible to processor 504, rendercomputer system 500 into a special-purpose machine that is customized toperform the operations specified in the instructions.

Computer system 500 further includes a read only memory (ROM) 508 orother static storage device coupled to bus 502 for storing staticinformation and instructions for processor 504. A storage device 510,such as a magnetic disk or optical disk, is provided and coupled to bus502 for storing information and instructions.

Computer system 500 may be coupled via bus 502 to a display 512, such asa cathode ray tube (CRT), for displaying information to a computer user.An input device 514, including alphanumeric and other keys, is coupledto bus 502 for communicating information and command selections toprocessor 504. Another type of user input device is cursor control 516,such as a mouse, a trackball, or cursor direction keys for communicatingdirection information and command selections to processor 504 and forcontrolling cursor movement on display 512. This input device typicallyhas two degrees of freedom in two axes, a first axis (e.g., x) and asecond axis (e.g., y), that allows the device to specify positions in aplane.

Computer system 500 may implement the techniques described herein usingcustomized hard-wired logic, one or more ASICs or FPGAs, firmware and/orprogram logic which in combination with the computer system causes orprograms computer system 500 to be a special-purpose machine. Accordingto one embodiment, the techniques herein are performed by computersystem 500 in response to processor 504 executing one or more sequencesof one or more instructions contained in main memory 506. Suchinstructions may be read into main memory 506 from another storagemedium, such as storage device 510. Execution of the sequences ofinstructions contained in main memory 506 causes processor 504 toperform the process steps described herein. In alternative embodiments,hard-wired circuitry may be used in place of or in combination withsoftware instructions.

The term “storage media” as used herein refers to any non-transitorymedia that store data and/or instructions that cause a machine tooperation in a specific fashion. Such storage media may comprisenon-volatile media and/or volatile media. Non-volatile media includes,for example, optical or magnetic disks, such as storage device 510.Volatile media includes dynamic memory, such as main memory 506. Commonforms of storage media include, for example, a floppy disk, a flexibledisk, hard disk, solid state drive, magnetic tape, or any other magneticdata storage medium, a CD-ROM, any other optical data storage medium,any physical medium with patterns of holes, a RAM, a PROM, and EPROM, aFLASH-EPROM, NVRAM, any other memory chip or cartridge.

Storage media is distinct from but may be used in conjunction withtransmission media. Transmission media participates in transferringinformation between storage media. For example, transmission mediaincludes coaxial cables, copper wire and fiber optics, including thewires that comprise bus 502. Transmission media can also take the formof acoustic or light waves, such as those generated during radio-waveand infra-red data communications.

Various forms of media may be involved in carrying one or more sequencesof one or more instructions to processor 504 for execution. For example,the instructions may initially be carried on a magnetic disk or solidstate drive of a remote computer. The remote computer can load theinstructions into its dynamic memory and send the instructions over atelephone line using a modem. A modem local to computer system 500 canreceive the data on the telephone line and use an infra-red transmitterto convert the data to an infra-red signal. An infra-red detector canreceive the data carried in the infra-red signal and appropriatecircuitry can place the data on bus 502. Bus 502 carries the data tomain memory 506, from which processor 504 retrieves and executes theinstructions. The instructions received by main memory 506 mayoptionally be stored on storage device 510 either before or afterexecution by processor 504.

Computer system 500 also includes a communication interface 518 coupledto bus 502. Communication interface 518 provides a two-way datacommunication coupling to a network link 520 that is connected to alocal network 522. For example, communication interface 518 may be anintegrated services digital network (ISDN) card, cable modem, satellitemodem, or a modem to provide a data communication connection to acorresponding type of telephone line. As another example, communicationinterface 518 may be a local area network (LAN) card to provide a datacommunication connection to a compatible LAN. Wireless links may also beimplemented. In any such implementation, communication interface 518sends and receives electrical, electromagnetic or optical signals thatcarry digital data streams representing various types of information.

Network link 520 typically provides data communication through one ormore networks to other data devices. For example, network link 520 mayprovide a connection through local network 522 to a host computer 524 orto data equipment operated by an Internet Service Provider (ISP) 526.ISP 526 in turn provides data communication services through the worldwide packet data communication network now commonly referred to as the“Internet” 528. Local network 522 and Internet 528 both use electrical,electromagnetic or optical signals that carry digital data streams. Thesignals through the various networks and the signals on network link 520and through communication interface 518, which carry the digital data toand from computer system 500, are example forms of transmission media.

Computer system 500 can send messages and receive data, includingprogram code, through the network(s), network link 520 and communicationinterface 518. In the Internet example, a server 530 might transmit arequested code for an application program through Internet 528, ISP 526,local network 522 and communication interface 518.

The received code may be executed by processor 504 as it is received,and/or stored in storage device 510, or other non-volatile storage forlater execution.

In the foregoing specification, embodiments of the invention have beendescribed with reference to numerous specific details that may vary fromimplementation to implementation. The specification and drawings are,accordingly, to be regarded in an illustrative rather than a restrictivesense. The sole and exclusive indicator of the scope of the invention,and what is intended by the applicants to be the scope of the invention,is the literal and equivalent scope of the set of claims that issue fromthis application, in the specific form in which such claims issue,including any subsequent correction.

What is claimed is:
 1. A mobile device comprising: one or moreprocessors; and one or more memories storing: first mapping data thatspecifies a mapping between a first gesture, a first device context, andone or more first device actions, second mapping data that specifies amapping between second gesture that is different than the first gesture,a second device context that is different than the first device context,and one or more second device actions that are different than the firstdevice actions; instructions which, when processed by the one or moreprocessors, cause the mobile device to: detect performance of agesturing event that is similar to both the first gesture and the secondgesture and determine that it cannot be determined whether the gesturingevent definitively corresponds to the first gesture or the secondgesture based upon the gesturing event alone, in response to determiningthat it cannot be determined whether the gesturing event definitivelycorresponds to the first gesture or the second gesture based upon thegesturing event alone, determine that the gesturing event definitivelycorresponds to the first gesture by: detecting that one or moreconditions pertaining to the mobile device, when the performance of thegesturing event was detected, correspond to the first device context andnot the second device context, and in response to detecting that one ormore conditions pertaining to the mobile device, when the performance ofthe gesturing event was detected, correspond to the first device contextand not the second device context, determining that the gesturing eventcorresponds to the first gesture and causing the mobile device toperform the one or more first device actions specified by the firstmapping data, instead of the one or more second device actions specifiedby the second mapping data.
 2. The mobile device as recited in claim 1,wherein the gesturing event is one or more of a motion event by themobile device, a motion event by a user, a touch-based event by a user,or a sound event.
 3. The mobile device as recited in claim 1, whereinthe first device context and the second device context include one ormore of: a geographical location of the mobile device, time,temperature, an amount of ambient light, detected presence of otherdevices, attributes of one or more applications on the mobile device, ora user associated with the mobile device.
 4. The mobile device asrecited in claim 1, wherein the first device context and the seconddevice context further include one or more of: characteristics of one ormore other devices within a specified proximity of the mobile device, orcharacteristics of a user associated with the mobile device.
 5. Themobile device as recited in claim 4, wherein the characteristics of oneor more other devices within a specified proximity of the mobile deviceare determined by the mobile device.
 6. The mobile device as recited inclaim 4, wherein the one or more of characteristics of one or more otherdevices within a specified proximity of the mobile device include one ormore of: one or more capabilities of the one or more other devices,ownership attributes of the one or more other devices, types of the oneor more other devices, or user accounts that correspond to the one ormore other devices.
 7. The mobile device as recited in claim 4, whereinthe characteristics of a user associated with the mobile device includeone or more of: an identity of the user, or one or more applications onthe mobile device currently being used by the user.
 8. One or morenon-transitory computer-readable media storing instructions which, whenprocessed by one or more processors, cause: detecting, by a mobiledevice, a gesturing event that is similar to both a first gesture and asecond gesture and determining that it cannot be determined whether thegesturing event definitively corresponds to the first gesture or thesecond gesture based upon the gesturing event alone, wherein firstmapping data specifies a mapping between the first gesture, a firstdevice context, and one or more first device actions, and second mappingdata specifies a mapping between the second gesture that is differentthan the first gesture, a second device context that is different thanthe first device context, and one or more second device actions that aredifferent than the first device actions, in response to determining thatit cannot be determined whether the gesturing event definitivelycorresponds to the first gesture or the second gesture based upon thegesturing event alone, determining, by the mobile device, that thegesturing event definitively corresponds to the first gesture by:detecting that one or more conditions pertaining to the mobile device,when the performance of the gesturing event was detected, correspond tothe first device context and not the second device context, and inresponse to detecting that one or more conditions pertaining to themobile device, when the performance of the gesturing event was detected,correspond to the first device context and not the second devicecontext, determining that the gesturing event corresponds to the firstgesture and causing the mobile device to perform the one or more firstdevice actions specified by the first mapping data, instead of the oneor more second device actions specified by the second mapping data. 9.The one or more non-transitory computer-readable media as recited inclaim 8, wherein the gesturing event is one or more of a motion event bythe mobile device, a motion event by a user, a touch-based event by auser, or a sound event.
 10. The one or more non-transitorycomputer-readable media as recited in claim 8, wherein the first devicecontext and the second device context include one or more of: ageographical location of the mobile device, time, temperature, an amountof ambient light, detected presence of other devices, attributes of oneor more applications on the mobile device, or a user associated with themobile device.
 11. The one or more non-transitory computer-readablemedia as recited in claim 8, wherein the first device context and thesecond device context further include one or more of: characteristics ofone or more other devices within a specified proximity of the mobiledevice, or characteristics of a user associated with the mobile device.12. The one or more non-transitory computer-readable media as recited inclaim 11, wherein the characteristics of one or more other deviceswithin a specified proximity of the mobile device are determined by themobile device.
 13. The one or more non-transitory computer-readablemedia as recited in claim 11, wherein the one or more of characteristicsof one or more other devices within a specified proximity of the mobiledevice include one or more of: one or more capabilities of the one ormore other devices, ownership attributes of the one or more otherdevices, types of the one or more other devices, or user accounts thatcorrespond to the one or more other devices.
 14. The one or morenon-transitory computer-readable media as recited in claim 11, whereinthe characteristics of a user associated with the mobile device includeone or more of: an identity of the user, or one or more applications onthe mobile device currently being used by the user.
 15. Acomputer-implemented method comprising: detecting, by a mobile device, agesturing event that is similar to both a first gesture and a secondgesture and determining that it cannot be determined whether thegesturing event definitively corresponds to the first gesture or thesecond gesture based upon the gesturing event alone, wherein firstmapping data specifies a mapping between the first gesture, a firstdevice context, and one or more first device actions, and second mappingdata specifies a mapping between the second gesture that is differentthan the first gesture, a second device context that is different thanthe first device context, and one or more second device actions that aredifferent than the first device actions, in response to determining thatit cannot be determined whether the gesturing event definitivelycorresponds to the first gesture or the second gesture based upon thegesturing event alone, determining, by the mobile device, that thegesturing event definitively corresponds to the first gesture by:detecting that one or more conditions pertaining to the mobile device,when the performance of the gesturing event was detected, correspond tothe first device context and not the second device context, and inresponse to detecting that one or more conditions pertaining to themobile device, when the performance of the gesturing event was detected,correspond to the first device context and not the second devicecontext, determining that the gesturing event corresponds to the firstgesture and causing the mobile device to perform the one or more firstdevice actions specified by the first mapping data, instead of the oneor more second device actions specified by the second mapping data. 16.The computer-implemented method as recited in claim 15, wherein thegesturing event is one or more of a motion event by the mobile device, amotion event by a user, a touch-based event by a user, or a sound event.17. The computer-implemented method as recited in claim 15, wherein thefirst device context and the second device context include one or moreof: a geographical location of the mobile device, time, temperature, anamount of ambient light, detected presence of other devices, attributesof one or more applications on the mobile device, or a user associatedwith the mobile device.
 18. The computer-implemented method as recitedin claim 15, wherein the first device context and the second devicecontext further include one or more of: characteristics of one or moreother devices within a specified proximity of the mobile device, orcharacteristics of a user associated with the mobile device.
 19. Thecomputer-implemented method as recited in claim 18, wherein the one ormore of characteristics of one or more other devices within a specifiedproximity of the mobile device include one or more of: one or morecapabilities of the one or more other devices, ownership attributes ofthe one or more other devices, types of the one or more other devices,or user accounts that correspond to the one or more other devices. 20.The computer-implemented method as recited in claim 18, wherein thecharacteristics of a user associated with the mobile device include oneor more of: an identity of the user, or one or more applications on themobile device currently being used by the user.